Add blog for implementing Kubernetes ConfigMap revisions with Pulumi and Argo Rollouts #15441
+320
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h Pulumi and Argo Rollouts This commit introduces a new blog post detailing the implementation of a custom ConfigMap revision system in Kubernetes using Pulumi's ConfigMapPatch and owner references. The solution addresses challenges faced during canary deployments, particularly with AWS Spot instances, by leveraging Kubernetes' garbage collection mechanism for automatic cleanup of ConfigMaps. Key highlights: - Overview of the problem with existing ConfigMap behavior during canary deployments - Detailed explanation of the solution using owner references and ConfigMapPatch - Code examples demonstrating the implementation - Benefits of the approach, including revision control and canary safety Additionally, a meta image for the blog post has been added.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new blog post detailing the implementation of a custom ConfigMap revision system in Kubernetes using Pulumi's ConfigMapPatch and owner references. The solution addresses challenges faced during canary deployments, particularly with AWS Spot instances, by leveraging Kubernetes' garbage collection mechanism for automatic cleanup of ConfigMaps.
Key highlights:
Additionally, a meta image for the blog post has been added.